Received: from digifix.com (digifix.digifix.com [198.133.162.23]) by
nic.hookup.net (8.6.beta.12/0.4) with SMTP id PAA04910; Mon,
27 Sep 1993 15:53:01 -0400
Received: by digifix.com id AA13816 (5.65c/IDA-1.4.4); Mon,
27 Sep 1993 15:52:55 -0400
Received: by NeXT.Mailer (1.95)
Received: by NeXT Mailer (1.95)
Date: Mon, 27 Sep 1993 15:52:55 -0400
From: Scott Anguish <sanguish@digifix.com>
Subject: Re: MiscKit summary and proposal: stirring up the ashes
To: Michael_Pizolato@afs.com
Cc: misckit@byu.edu
Reply-To: sanguish@digifix.com
Message-Id: <199309271952.AA13816@digifix.com>
Content-Transfer-Encoding: 7BIT
Status: O
>Is the fact that these "are all pretty much supported by NeXT"
>documented anywhere? I know there's something about the compiler
>and/or linker search paths including /LocalDeveloper, but I'm
>unaware of support for such subdirectories as Documentation and
>Source. Here's the hierarchy I prefer (which we use here, and
>which I also have duplicated under ~/Developer for my own private
>work):
After I originally mailed that to Don and the list, Don told me that infact lib is not searched, so I'm definately going to change mine to Libraries as well.
It seems logical to put the documentation with the classes. As for the source... I wouldn't consider the MiscKit stuff to be example's as such, so I'm thinking that that might be a good place for it.
The reason I brought that up is that I want to address the issue of hardwired Makefiles now, instead of later.
How things are arranged on anyones machine is their business, I just don't want the installation and upgrading of MiscKit to be a hassle.
>I could be confused (easy for me ;-), but I think Scott is proposing
>a setup for the source distribution, rather than a setup for Don
>or individual contributors to maintain sources.
Thats about what I was after.
>Anyway, I personally
>find it interesting to see how others have their project directories
>structured. The structures I have seen so far that are used by